home *** CD-ROM | disk | FTP | other *** search
- Path: nntp.teleport.com!sschaem
- From: sschaem@teleport.com (Stephan Schaem)
- Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.programmer
- Subject: Re: toy operating systems, like AmigaOS
- Date: 15 Apr 1996 07:39:58 GMT
- Organization: Teleport - Portland's Public Access (503) 220-1016
- Message-ID: <4ksuge$haa@nadine.teleport.com>
- References: <skllsf.984983.4.5@groomlake.mil> <4krdlk$jge@vixen.cso.uiuc.edu>
- NNTP-Posting-Host: julie.teleport.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- howard daniel joseph (djhoward@students.uiuc.edu) wrote:
- : Duanne Barry (dbarry@groomlake.mil) wrote:
-
- : : I've just spent the last 2 months coding a large and complex algorithm
- : : on a Unix box (Sun Sparc 10).
-
- : : I've have made hundreds of critical bugs that generally
- : : just cause the entire code to blow up (eg. memory overwriting, runaway
- : : loops, etc). But never ever did any of my bugs actually crash the Unix box
- : : (ie. it never needed a reboot) due to the lovely memory protection.
-
- : Well, there are two ways to go about this;
-
- : 1) Don't write shitty code.
-
- More easy said then done... this can be possible on very simple project.
- but write >200,000 C line project.. compile, I'm sure you will have
- plenty of bug already here... should your compiler crash and burn
- because you made a syntax error?!
- And after that, how many people can really say they wrote complex
- project with zero bug on the first go?! How much time was involve
- in proof reading/desecting the functions/system?
-
- : 2) Write shitty code on a platform that supports shitty code.
-
- This make no sense...
-
- : 3) If you want to take the shit out of your code without crashing
- : a system without memory protection, whack your shit around in a more
- : robust environment and then send your shitless code to the Amiga. :)
-
- For Raw code that a very good idea indeed! Run netbsd, and just port :)
-
- Stephan
-
-